#989: allow expressions in template variable definitions by Paras14 · Pull Request #2282 · devonfw/IDEasy

Paras14 · 2026-08-06T14:41:36Z

This PR fixes #989

Implements #989 and supersedes the $[ask:...] / $[secret:...] syntax of #2179.

Closes #2165.

Implemented changes

Added new package com.devonfw.tools.ide.expression with the expression syntax @«function-name»([«arg»[,«arg»]*]) resolved during variable resolution.
ExpressionFunction - interface implemented by every function.
ExpressionFunctionManager - registry to look up functions by name so further functions can be registered with new IDEasy releases.
ExpressionParser - locates function calls and parses their arguments. A RegEx is only used to locate the start of a call, the argument list is scanned manually since a RegEx cannot express a balanced list of arguments containing quoted commas, quoted parenthesis or nested calls.
ExpressionContext - gives a function access to the IdeContext, variable lookup and persistence.
Added function @path(«path»[, unix|native]) that normalises a path, by default replacing backslashes with slashes.
Added functions @ask-variable(«name»[, «question»[, «default»]]) and @ask-secret(...) with masked input. An already defined variable is returned without asking, an empty 1st argument always asks, and an empty string as 3rd argument permits empty input.
Added functions @if-windows, @if-mac, @if-linux and @if-unix that insert their argument if the OS matches.
Added IdeContext.askForSecret(String, String) analogous to askForInput. AbstractIdeContext implements the prompt loop and the batch mode contract and delegates reading to the new protected readSecretLine(), which IdeContextConsole overrides with Console.readPassword().
Values entered for a workspace template are persisted to conf/ide.properties so the question is only asked the first time. A value that could not be asked for in batch mode is not persisted.
Arguments are resolved through the regular variable resolution, so a String argument may itself contain variables (e.g. @path('$[IDE_HOME]/software/node')).
Text that does not call a registered function is left untouched.

Testing instructions

Masked input needs a real console, so run this from a normal terminal and not from the IDE.

Build the branch and dump the classpath, from the repository root:

mvn -pl cli -am install -DskipTests
mvn -pl cli dependency:build-classpath "-Dmdep.outputFile=cp.txt"
$CP = (Get-Content cli\cp.txt -Raw).Trim()
$CLASSES = "C:\projects\IDEasy\workspaces\main\IDEasy\cli\target\classes"

(make sure you add your path correctly for the cli target classes: "\cli\target\classes")

In a test project create IDEasy\settings\workspace\update\ai-test.properties:

ai.backend.url=@ask-variable('MY_URL')
ai.api.key=@ask-secret('MY_TOKEN', 'Enter your API key (from the portal):')
ai.node.path=@path('$[IDE_HOME]/software/node/node', native)
ai.other=@ask-secret('MY_OPTIONAL', 'Password (may be empty):', '')

Make sure MY_URL, MY_TOKEN and MY_OPTIONAL are not yet defined in IDEasy\conf\ide.properties.

From the project directory, run the local build:

java -cp "$CLASSES;$CP" com.devonfw.tools.ide.cli.Ideasy update

You are asked three times. MY_URL is echoed while typing, MY_TOKEN and MY_OPTIONAL are not. The question for MY_TOKEN is shown as given, including the parenthesis. Press enter without typing anything for MY_OPTIONAL.
IDEasy\workspaces\main\ai-test.properties contains the three entered values and ai.node.path with backslashes. IDEasy\conf\ide.properties contains MY_URL, MY_TOKEN and MY_OPTIONAL.
Run again. There is no prompt and the file keeps the same values.
Remove MY_URL, MY_TOKEN and MY_OPTIONAL from IDEasy\conf\ide.properties and run again with --batch. There is no prompt, the workspace merge fails with CliAbortException: Aborted by end-user. and nothing is added to IDEasy\conf\ide.properties, as an undefined variable cannot be asked for in batch mode.

Checklist for this PR

Make sure everything is checked before merging this PR. For further info please also see
our DoD.

When running mvn clean test locally all tests pass and build is successful
PR title is of the form #«issue-id»: «brief summary» (e.g. #921: fixed setup.bat). If no issue ID exists, title only.
PR top-level comment summarizes what has been done and contains link to addressed issue(s)
PR and issue(s) have suitable labels
Issue is set to In Progress and assigned to you or there is no issue (might happen for very small PRs)
You followed all coding conventions
You have added the issue implemented by your PR in CHANGELOG.adoc unless issue is labeled
with internal
You have formulated clear instructions on how to test your contribution under "Testing instructions"

…d in batch mode

…/989-expression-functions

coveralls · 2026-08-07T09:01:20Z

Coverage Report for CI Build 33495019591

Coverage increased (+0.2%) to 73.819%

Details

Coverage increased (+0.2%) from the base build.
Patch coverage: No coverable lines changed in this PR.
229 coverage regressions across 9 files.

Uncovered Changes

No uncovered changes found.

Coverage Regressions

229 previously-covered lines in 9 files lost coverage.

File	Lines Losing Coverage	Coverage
com/devonfw/tools/ide/context/AbstractIdeContext.java	173	71.88%
com/devonfw/tools/ide/environment/AbstractEnvironmentVariables.java	18	82.66%
com/devonfw/tools/ide/context/IdeContext.java	17	76.92%
com/devonfw/tools/ide/context/IdeContextConsole.java	7	0.0%
com/devonfw/tools/ide/merge/FileMerger.java	7	86.96%
com/devonfw/tools/ide/environment/EnvironmentVariablesMap.java	3	81.82%
com/devonfw/tools/ide/environment/SortedProperties.java	2	53.49%
com/devonfw/tools/ide/tool/ide/IdeToolCommandlet.java	1	87.42%
com/devonfw/tools/ide/version/VersionSegment.java	1	91.34%

Coverage Stats


Relevant Lines:	18583
Covered Lines:	14335
Line Coverage:	77.14%
Relevant Branches:	8276
Covered Branches:	5492
Branch Coverage:	66.36%
Branches in Coverage %:	Yes
Coverage Strength:	3.29 hits per line

💛 - Coveralls

Updated changelog for version 2026.08.002, including new features and bugfixes.

…ion-functions # Conflicts: # CHANGELOG.adoc

maybeec

Thanks for this PR, and thanks in particular for the parser itself. Locating a call with a RegEx and then scanning the argument list by hand is exactly the right call: findClosingParenthesis / parseArguments handle quoted commas, quoted parenthesis and nesting correctly, and the parametrized testForeignExpressionIsUntouched covering @media, @include, @Override and "@angular/core" is precisely the test I would have asked for. Passing unknown functions through untouched is the single most important property of this feature and you got it right and covered it. The JavaDoc on the new types is also good.

No blockers, and nothing below needs a redesign. The two I care most about are the plaintext handling of @ask-secret values and @path(..., native) not using WindowsPathSyntax.

Should-fix

@ask-secret values are persisted and logged in clear text - AbstractEnvironmentVariables.java:414
@path(..., native) hand-rolls separator replacement instead of WindowsPathSyntax - PathFunction.java:51
isPersistent() is hard-coded to true, so the "settings templates must not persist" requirement of #989 is not actually implemented - AbstractEnvironmentVariables.java:422, and its test only exercises a test double - ExpressionParserTest.java:198
askForSecret is a verbatim copy of askForInput - AbstractIdeContext.java:1108
DirectoryMergerExpressionTest depends on Hashtable iteration order - DirectoryMergerExpressionTest.java:34
The masking itself has no automated coverage, and the Windows git-bash path needs a manual test pass - IdeContextConsole.java:65
The new expression syntax is not documented anywhere - CHANGELOG.adoc:9
A template authoring error aborts ide update with a raw IllegalArgumentException - ExpressionParser.java:89

Minor

Secrets are trim()ed - AbstractIdeContext.java:1121
Function results are re-scanned by the variable resolver - AbstractEnvironmentVariables.java:214
AbstractIdeContextTest.TEST_RESOURCES already exists - DirectoryMergerExpressionTest.java:36
Redundant initial matcher.find() - ExpressionParser.java:57

Scope against #989

Requirement	Status
`@<function-name>([<arg>[,<arg>]*])` syntax, args always String, comma separated, trimmed, quoted with `'` or `"`	met
Args may themselves contain variables	met
Manual argument scanning instead of a pure RegEx	met, and better than the RegEx sketched in the issue
`@path` with 1st arg path, optional 2nd arg `unix` (default) / `native`	partial - `native` does not use `WindowsPathSyntax` (see 2)
`@ask-variable` / `@ask-secret`, defined variable returned without asking, empty 1st arg always asks, default question text, 3rd arg default value	met
Values from a workspace template persisted to `conf/ide.properties`	met
"For settings templates this should not happen since these templates are only instantiated once"	missing (see 3)
`@if-windows` / `@if-mac` / `@if-linux` / `@if-unix`	met
`ExpressionFunction` interface + `ExpressionFunctionManager` registry so new releases can register more functions	met

Also: the issue invites a follow-up story for the maven settings.xml password prompting/encryption (@ask-maven-secret or a resolve flag telling the function it is resolving settings.xml). Worth creating it and linking it here so the plaintext-storage topic from finding 1 has an owner.

CI / DoD

All checks green, CLA signed, branch is up-to-date with main, CHANGELOG entry present under the correct milestone, PR title follows #989: .... One nit: the commit Update CHANGELOG for version 2026.08.002 does not follow the #<issue-id>: <summary> commit format (see documentation/contributing/commit.adoc).

QuangAnhLe · 2026-08-17T08:15:39Z

Thanks for the PR. Most of my review points align with those of @maybeec mentioned earlier, so you can simply refer to my summary below; I won't be reviewing each section individually. Please feel free to contact me if you have any questions.

Review: #989 — expression functions for template variables

Overall: solid, well-tested implementation. The architecture matches the ticket's design (interface + manager + parser + per-OS/path/ask functions), the parser correctly handles what a regex
can't (quoted commas, quoted parens, nesting), foreign @... syntax is passed through untouched, and the test suite is thorough (33 tests: parser unit tests, integration through
EnvironmentVariables, and a real DirectoryMerger run). All pass. Commit messages are clean. The core logic is correct.

Below are findings, most-severe first. None block merge; the first two are worth a decision.

1. Secret values flow into logs in plaintext (masking only applies to keystrokes)

@ask-secret masks input while typing, but the returned value is then treated as an ordinary variable value. The integration test's own output shows it:
Set variable 'AI_API_KEY=sk-TOPSECRET' in ...conf\ide.properties
That log line comes from PropertiesMerger (pre-existing), but it's newly reachable now that a secret can be the value being set. The value also lands in conf/ide.properties in cleartext — which
is the intended persistence, so that's fine. But the console/log echo of the secret is a real exposure for the "secret" case the ticket is trying to protect. Worth confirming intent; if
secrets are meant to stay off the log, this path (and any other value-logging) should be masked for @ask-secret results.

2. isPersistent() is hardcoded true — settings templates persist too (spec deviation)

AbstractEnvironmentVariables.EnvironmentExpressionContext.isPersistent() (line 421–423) always returns true, so @ask-variable/@ask-secret persist to conf/ide.properties even when resolved from
a settings template. The ticket is explicit:

"For settings templates this should not happen since these templates are only instantiated once."

The Javadoc on ExpressionContext.isPersistent() (line 41–44) even documents the intended distinction, but the implementation doesn't make it — it has no way to tell whether the current
resolution is a settings vs. workspace template. Impact is low in practice (settings are instantiated once, so the "asked only once" benefit rarely matters), but the behavior contradicts the
spec and the doc. Either implement the settings/workspace distinction or soften the Javadoc/commit claim. Note the unit test testSettingsTemplateDoesNotPersist only exercises a hand-rolled
TestExpressionContext with persistent=false — it doesn't prove the real AbstractEnvironmentVariables path honors the setting, so this gap is masked in tests.

3. A defined variable's value returned by @ask-variable is not re-resolved for nested expressions

In AskFunction.apply, the defined-variable fast path returns context.getVariable(...) directly (line 71–73). That value is appended into value2 and then $[...] variables are resolved once more
by resolveWithSyntax, but embedded @... expressions inside an already-defined variable's value would not be, since apply's return is never fed back through the expression parser. This is an
asymmetry (a plain $[FOO] whose value contains @path(...) behaves the same — also not re-resolved — so it's consistent with existing variable semantics, but worth knowing). Edge case, low
priority; flagging for completeness.

4. Minor

readSecretLine fallback is unmasked: when System.console() is null (piped input, running from the IDE), IdeContextConsole.readSecretLine() logs a warning and reads via the plaintext Scanner.
Acceptable given the constraints, and it correctly warns, but it's worth ensuring the manual-testing doc emphasizes "run from a normal terminal" (it does — good).
No way to escape a quote inside a quoted argument. Backslash is deliberately not an escape char (correct, tested), so a literal ' inside a single-quoted arg is unrepresentable. Fine for KISS;
just a documented limitation.
EXTRA_CAPACITY = 8 is duplicated in both ExpressionParser (line 31) and AbstractEnvironmentVariables (line 34). Harmless, but could be a shared constant.
resolve() double-find: the guard if (!matcher.find()) (line 57) is followed by while (matcher.find(pos)) from pos=0, so the first match is found twice. Correct but slightly wasteful.

Suggested before merge

Items 1 and 2 are the only ones needing a judgment call — decide whether secrets should be masked in logs and whether the settings-vs-workspace persistence distinction is in scope now or a follow-up. Everything else is optional polish. The implementation and tests otherwise meet the Definition of Done for the core story.

…functions

…al error

gitguardian · 2026-08-25T08:14:29Z

⚠️ GitGuardian has uncovered 1 secret following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

Since your pull request originates from a forked repository, GitGuardian is not able to associate the secrets uncovered with secret incidents on your GitGuardian dashboard.
Skipping this check run and merging your pull request will create secret incidents on your GitGuardian dashboard.

🔎 Detected hardcoded secret in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
-	-	Generic High Entropy Secret	`3b2dd8c`	cli/src/test/java/com/devonfw/tools/ide/expression/ExpressionParserTest.java	View secret

🛠 Guidelines to remediate hardcoded secrets

Understand the implications of revoking this secret by investigating where it is used in your code.
Replace and store your secret safely. Learn here the best practices.
Revoke and rotate this secret.
If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

following these best practices for managing and storing secrets including API keys and other credentials
install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}

…d ordering

hohwille

@Paras14 thank you for your PR. This is really great work and you already included more than I was hoping for. Your implementation seems solid and functional. Awesome job 🥇
I left comments for improvement. My suggestion would be that you have a look what can be done very easy and quick and create a follow up issue for the rest so we can resolve these comments here and merge this PR which is already great as is. Thanks 🙏

hohwille · 2026-08-31T06:55:51Z

+=== Functions
+
+* `@path` normalizes a path.
+The first argument is the path.
+The second argument is optional and is the literal value `unix` (the default, which replaces backslashes with slashes) or `native` (which on Windows uses `WindowsPathSyntax.WINDOWS` and therefore backslashes).
+This is the remedy for values that come out with a mixed up path syntax on Windows, e.g.
+`$[IDE_HOME]/software/node/node.exe` resolves to `D:\projects\my-project/software/node/node.exe` where the backslashes of the drive letter and the slashes of the rest clash.
+
+[source]
+----
+@path('$[IDE_HOME]/software/node/node', unix)
+@path('$[IDE_HOME]/software/node/node.exe', native)
+----
+* `@ask-variable` asks the user for the value of a variable in plain text, and `@ask-secret` does the same but reads the input with masked input.
+The first argument is the name of the requested variable.
+If the variable is already defined it is returned without asking.
+If the empty string is given, the user is always asked and nothing is persisted.
+The second argument is an optional explicit question used as the prompt.
+If omitted, it defaults to `Please enter the value for the (secret) variable «NAME»:` and is required if the first argument is empty.
+The third argument is an optional configuration location to persist the entered value to, analogous to the `--cfg` option: `settings`, `workspace`, `conf` or `home` (default: `conf`).
+The fourth argument is an optional default value that is appended to the question in angled brackets so the user can just press return.
+Provide the empty string (`''`) to allow an empty value.
+If omitted or given as `null`, an empty value is not allowed and the user is asked again.
+
+[source]
+----
+@ask-variable('AI_BACKEND_URL')
+@ask-variable('AI_BACKEND_URL', 'Please enter the LLM backend URL:', conf, 'http://localhost:1234')
+@ask-secret('AI_API_KEY', 'Please enter your API key:', conf)
+----
+* `@if-windows`, `@if-mac`, `@if-linux` and `@if-unix` insert their single argument only if the current operating system matches and otherwise resolve to the empty string.
+This allows to select an OS specific value inline.
+
+[source]
+----
+$[IDE_HOME]/software/mvn/bin/mvn@if-windows('.bat')@if-unix('.sh')
+----
+
+A function that is not registered by `IDEasy` is passed through entirely untouched.
+This is essential since foreign configuration formats may use an `@` for their own purposes (e.g. a CSS rule `@media(max-width:600px)` or an Eclipse `@param`) and `IDEasy` must never try to resolve placeholders that are not its own.
+
+=== Where the values of `@ask-*` are stored and how to use the functions
+
+* The value entered for an `@ask-*` call is persisted to the `ide.properties` of the chosen configuration location so that the user is asked only once.
+In particular, the value entered for `@ask-secret` is _not_ encrypted; it is stored as plain text in `conf/ide.properties`.
+That file is user-local and is not committed to git, and the value is masked in all log output, but the file itself is readable on the machine.
+Encryption is a separate follow-up story (it also covers the case of the Maven `settings.xml`).
+* Expressions belong in the workspace templates under `setup` and `update`.
+Do not put an `@ask-*` call into a value of `ide.properties` itself: a value that contains an expression is resolved on _every_ variable resolution, so a `@ask-*` in `ide.properties` would prompt on every `ide` invocation (including `ide env`).
+Expressions are typically used in the `update` templates to build up OS-specific or user-specific settings that would otherwise be hard to express with a plain variable, as in the following example that only resolves to a working value on the matching operating system:
+
+[source]
+----
+<local-interpreter path="@path('$[IDE_HOME]/software/node/node', native)" merge:id="name()"/>
+----
+


This is great but I fear that this way it will be hard to keep the documentation in sync with the code.
Maybe we can use docjar and just link to the latest JavaDoc of the functions package.
If we later follow my suggestions to express function arguments more structural with generic parsing support rather than manual handling in apply method implementation the JavaDoc itself would be fully sufficient to lookup what is needed. Otherwise we can also just put a link to the package in the GitHub source-code.

This is valid point, let's move this to a separate issue, since linking the JavaDoc (or the GitHub source) and reworking the docs is best done on its own to keep them in sync.
@hohwille

…ion-functions # Conflicts: # CHANGELOG.adoc

…/Paras14/IDEasy into feature/989-expression-functions # Conflicts: # CHANGELOG.adoc

…uilder capacity)

… @ask-secret values

…nstead of a mock context

Co-authored-by: Jörg Hohwiller <hohwille@users.noreply.github.com>

…ample

Paras14 added 3 commits August 6, 2026 09:55

devonfw#989: add expression function framework for template variables

8762376

devonfw#989: resolve expressions during variable resolution

a41eace

devonfw#989: do not persist template variables that could not be aske…

d1945db

…d in batch mode

github-project-automation Bot added this to IDEasy board Aug 6, 2026

github-project-automation Bot moved this to 🆕 New in IDEasy board Aug 6, 2026

Paras14 self-assigned this Aug 6, 2026

Paras14 moved this from 🆕 New to Team Review in IDEasy board Aug 6, 2026

Paras14 added enhancement New feature or request configuration should be configurable or configuration change settings ide-settings repo and replated processes and features merger workspace template merger (XML, JSON, properties) ready-to-implement labels Aug 6, 2026

hohwille assigned QuangAnhLe Aug 7, 2026

Paras14 added 2 commits August 7, 2026 10:50

Merge branch 'main' of https://github.com/devonfw/ideasy into feature…

b315917

…/989-expression-functions

devonfw#989: Fix formatting issues

c01ce8c

Paras14 and others added 3 commits August 12, 2026 11:58

Update CHANGELOG for version 2026.08.002

53b84ea

Updated changelog for version 2026.08.002, including new features and bugfixes.

Merge branch 'main' into feature/989-expression-functions

39cbef5

Merge remote-tracking branch 'upstream/main' into feature/989-express…

0af5ed9

…ion-functions # Conflicts: # CHANGELOG.adoc

maybeec reviewed Aug 16, 2026

View reviewed changes

hohwille mentioned this pull request Aug 24, 2026

Support for variables and expressions in repository URL #2366

Open

Paras14 added 6 commits August 25, 2026 01:11

devonfw#989: Add config location and default value arguments to @ask …

3aa99ce

…functions

devonfw#989: Use WindowsPathSyntax for @path with native mode

cb7b7cf

devonfw#989: Report template errors as CliException instead of intern…

3e4dedc

…al error

devonfw#989: Mask secret variable values in log output

3b2dd8c

devonfw#989: Do not print a stacktrace for expected template errors

ca3d70b

devonfw#989: Merge upstream/main into 989-expression-functions

7a74b11

Paras14 moved this from Team Review to 👀 In review in IDEasy board Aug 25, 2026

Paras14 and others added 4 commits August 26, 2026 09:18

devonfw#989: address review findings on documentation, duplication an…

07af2e2

…d ordering

Merge branch 'main' into feature/989-expression-functions

6f4068b

devonfw#989: Rename test values that look like real API keys

87828e4

Merge branch 'main' into feature/989-expression-functions

32cddc4

hohwille approved these changes Aug 31, 2026

View reviewed changes

hohwille reviewed Aug 31, 2026

View reviewed changes

Comment thread cli/src/test/java/com/devonfw/tools/ide/expression/ExpressionParserTest.java Outdated

hohwille and others added 8 commits August 31, 2026 18:08

Merge branch 'main' into feature/989-expression-functions

438026a

Merge remote-tracking branch 'upstream/main' into feature/989-express…

cceae5f

…ion-functions # Conflicts: # CHANGELOG.adoc

Merge branch 'feature/989-expression-functions' of https://github.com…

a42b7e5

…/Paras14/IDEasy into feature/989-expression-functions # Conflicts: # CHANGELOG.adoc

devonfw#989: tidy ExpressionParser (regex group comment, drop StringB…

8e19764

…uilder capacity)

devonfw#989: show @ask default in square brackets and stop persisting…

d81e4e9

… @ask-secret values

devonfw#989: test expressions through the real EnvironmentVariables i…

de79305

…nstead of a mock context

Update documentation/configurator.adoc

02eba72

Co-authored-by: Jörg Hohwiller <hohwille@users.noreply.github.com>

devonfw#989: drop the no-op conf location from the @ask-secret doc ex…

d750d01

…ample

quando632 mentioned this pull request Sep 1, 2026

#2366: support variables and expressions in repository properties #2398

Draft

9 tasks

Uh oh!

Conversation

Paras14 commented Aug 6, 2026

This PR fixes #989

Implemented changes

Testing instructions

Checklist for this PR

Uh oh!

coveralls commented Aug 7, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Coverage Report for CI Build 33495019591

Coverage increased (+0.2%) to 73.819%

Details

Uncovered Changes

Coverage Regressions

Coverage Stats

💛 - Coveralls

Uh oh!

maybeec left a comment

Choose a reason for hiding this comment

Should-fix

Minor

Scope against #989

CI / DoD

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

QuangAnhLe commented Aug 17, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

gitguardian Bot commented Aug 25, 2026

⚠️ GitGuardian has uncovered 1 secret following the scan of your pull request.

Uh oh!

hohwille left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

hohwille Aug 31, 2026

Choose a reason for hiding this comment

Uh oh!

Paras14 Sep 1, 2026

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

5 participants

coveralls commented Aug 7, 2026 •

edited

Loading

QuangAnhLe commented Aug 17, 2026 •

edited

Loading